Skip to content

Conversation

@hiyouga
Copy link
Owner

@hiyouga hiyouga commented Jan 9, 2026

What does this PR do?

Fixes # (issue)

Before submitting

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @hiyouga, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a minor but important bug in the parameter parsing logic. It rectifies an erroneous check that incorrectly validated FP8 training compatibility by looking at the wrong argument source. The fix ensures that the system correctly identifies when FP8 training is incompatible with quantization settings, improving the robustness of argument validation.

Highlights

  • FP8 Training Compatibility Fix: Corrected a validation check for FP8 training to properly reference model_args.quantization_bit instead of training_args.quantization_bit, resolving an incorrect compatibility check.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes an issue with argument validation for FP8 training by changing training_args.quantization_bit to model_args.quantization_bit. The change is correct and necessary. I've also identified a related bug in the same file concerning fp8 argument handling and have left a comment on the change with a suggestion to fix it as part of this PR for completeness.

raise ValueError("GaLore and APOLLO are incompatible with DeepSpeed yet.")

if training_args.fp8 and training_args.quantization_bit is not None:
if training_args.fp8 and model_args.quantization_bit is not None:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This fix is correct! While reviewing, I noticed another related issue with fp8 argument handling in this file. On line 364, model_args.fp8 is assigned a value. However, the fp8 attribute is defined in TrainingArguments, not ModelArguments. This will cause an AttributeError if that code path is executed. To make this fp8 fix complete, could you please also change line 364 to training_args.fp8 = True?

@hiyouga hiyouga merged commit d7d734d into main Jan 9, 2026
17 checks passed
@hiyouga hiyouga deleted the f branch January 9, 2026 08:17
@hiyouga hiyouga added the solved This problem has been already solved label Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

solved This problem has been already solved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants